Fix magic link first-load redirects#37
Merged
Merged
Conversation
Ensure URL magic-link tokens are used immediately on first load and delay protected remote data fetches until the access session has been verified, preventing staff pages from redirecting home before auth resolves. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
✅ Deploy Preview for kid-a ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opening a staff magic link directly could briefly render as a guest before the access session finished resolving, which caused protected pages like
/desk?token=...to redirect home on the first visit. The same link then worked on a second navigation because the token had already been stored.This change makes the active magic-link token come from the current URL before falling back to session storage, so first-load requests can authenticate immediately. It also waits until the remote access session is ready before loading protected remote event data, avoiding unauthorized fetches during startup.
Validation:
npm run lintnpm run build:netlify